chore(deps): update dependency @biomejs/biome to v1.9.0 #418

renovate · 2024-06-10T13:53:56Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@biomejs/biome (source)	`1.8.0` -> `1.9.0`

Release Notes

biomejs/biome (@biomejs/biome)

`v1.9.0`

Compare Source

Analyzer

Implement the semantic model for CSS. Contributed by @togami2864

CLI

New features

Add --graphql-linter-enabled option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @ematipico
New EXPERIMENTAL search command. The search command allows you to search a Biome project using GritQL syntax.

GritQL is a powerful language that lets you do structural searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.

While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.

For now, the search command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know your issues!

Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put single quotes around your Grit queries.
```
biome search '`console.log($message)`' # find all `console.log` invocations
```
Contributed by @arendjr and @BackupMiles

The option --max-diagnostics now accept a none value, which lifts the limit of diagnostics shown. Contributed by @ematipico

Add a new reporter --reporter=gitlab, that emits diagnostics for using the GitLab Code Quality report.

[
  {
    "description": "Use === instead of ==. == is only allowed when comparing against `null`",
    "check_name": "lint/suspicious/noDoubleEquals",
    "fingerprint": "6143155163249580709",
    "severity": "critical",
    "location": {
      "path": "main.ts",
      "lines": {
        "begin": 4
      }
    }
  }
]

Contributed by @NiclasvanEyk

Add new options to the lsp-proxy and start commands:
- --log-path: a directory where to store the daemon logs. The commands also accepts the environment variable BIOME_LOG_PATH.
- --log-prefix-name: a prefix that's added to the file name of the logs. It defaults to server.log. The commands also accepts the environment variable BIOME_LOG_PREFIX_NAME.
@Contributed by @ematipico

Enhancements

When a --reporter is provided, and it's different from the default one, the value provided by via --max-diagnostics is ignored and the limit is lifted. Contributed by @ematipico
biome init now generates a new config file with more options set.
This change intends to improve discoverability of the options and to set the more commonly used options to their default values.
Contributed by @Conaclos

The --verbose flag now reports the list of files that were evaluated, and the list of files that were fixed.
The evaluated files are the those files that can be handled by Biome, files that are ignored, don't have an extension or have an extension that Biome can't evaluate are excluded by this list.
The fixed files are those files that were handled by Biome and changed. Files that stays the same after the process are excluded from this list.

 VERBOSE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Files processed:

  - biome/biome.json
  - biome/packages/@&#8203;biomejs/cli-win32-arm64/package.json
  - biome/packages/tailwindcss-config-analyzer/package.json

 VERBOSE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Files fixed:

  - biome/biome/packages/tailwindcss-config-analyzer/src/generate-tailwind-preset.ts

Contributed by @ematipico

Allow passing nursery to the --only and --skip filters.

The --only option allows you to run a given rule or rule group.
The --skip option allows you to skip the execution of a given group or a given rule.

Previously, it was not possible to pass nursery.
This restriction is now removed, as it may make sense to skip the nursery rules that a project has enabled.

Contributed by @Conaclos
The CLI now returns an error code when calling a command in stdin mode, and the contents of the files aren't fixed. For example, the following example will result in an error code of 1 because the lint command triggers some lint rules:
```
echo "let x = 1" | biome lint --stdin-file-path=stdin.js
```
Contributed by @ematipico

Bug fixes

biome lint --write now takes --only and --skip into account (#3470). Contributed by @Conaclos
Fix #3368, now the reporter github tracks the diagnostics that belong to formatting and organize imports. Contributed by @ematipico
Fix #3545, display a warning, 'Avoid using unnecessary Fragment,' when a Fragment contains only one child element that is placed on a new line. Contributed by @satojin219
Migrating from Prettier or ESLint no longer overwrite the overrides field from the configuration (#3544). Contributed by @Conaclos
Fix JSX expressions for noAriaHiddenOnFocusable (#3708). Contributed by @anthonyshew
Fix edge case for <canvas> elements that use role="img" (#3728). Contributed by @anthonyshew
Fix #3633, where diagnostics where incorrectly printed if the code has errors. Contributed by @ematipico
Allow aria-label on heading to prevent useHeadingContent diagnostic (#3767). Contributed by @anthonyshew
Fix edge case #3791 for rule noFocusedTests being used with non-string-like expressions (#3793). Contributed by @h-a-n-a
Fix optional ARIA properties for role="separator" in useAriaPropsForRole (#3856). Contributed by @anthonyshew

Configuration

Add support for loading configuration from .editorconfig files (#1724).

Configuration supplied in .editorconfig will be overridden by the configuration in biome.json. Support is disabled by default and can be enabled by adding the following to your formatter configuration in biome.json:
```
{
  "formatter": {
    "useEditorconfig": true
  }
}
```
Contributed by @dyc3

overrides from an extended configuration is now merged with the overrides of the extension.

Given the following shared configuration biome.shared.json:

{
  "overrides": [
    {
      "include": ["**/*.json"],
      // ...
    }
  ]
}

and the following configuration:

{
  "extends": ["./biome.shared.json"],
  "overrides": [
    {
      "include": ["**/*.ts"],
      // ...
    }
  ]
}

Previously, the overrides from biome.shared.json was overwritten.
It is now merged and results in the following configuration:

{
  "extends": ["./biome.shared.json"],
  "overrides": [
    {
      "include": ["**/*.json"],
      // ...
    },
    {
      "include": ["**/*.ts"],
      // ...
    }
  ]
}

Contributed by @Conaclos

Editors

Fix #3577, where the update of the configuration file was resulting in the creation of a new internal project. Contributed by @ematipico
Fix #3696, where biome.jsonc was incorrectly parsed with incorrect options. Contributed by @ematipico

Formatter

The CSS formatter is enabled by default. Which means that you don't need to opt-in anymore using the configuration file biome.json:
```
{
-  "css": {
-    "formatter": {
-      "enabled": true
-    }
-  }
}
```
Contributed by @ematipico
Add parentheses for nullcoalescing in ternaries.

This change aligns on Prettier 3.3.3.
This adds clarity to operator precedence.
```
- foo ? bar ?? foo : baz;
+ foo ? (bar ?? foo) : baz;
```
Contributed by @Conaclos
Keep the parentheses around infer ... extends declarations in type unions and type intersections (#3419). Contributed by @Conaclos
Keep parentheses around a yield expression inside a type assertion.

Previously, Biome removed parentheses around some expressions that require them inside a type assertion.
For example, in the following code, Biome now preserves the parentheses.
```
function* f() {
  return <T>(yield 0);
}
```
Contributed by @Conaclos

Remove parentheses around expressions that don't need them inside a decorator.

Biome now matches Prettier in the following cases:

  class {
-   @&#8203;(decorator)
+   @&#8203;decorator
    method() {}
  },
  class {
-   @&#8203;(decorator())
+   @&#8203;decorator()
    method() {}
  },
  class {
    @&#8203;(decorator?.())
    method() {}
  },

Contributed by @Conaclos

Keep parentheses around objects preceded with a @satisfies comment.

In the following example, parentheses are no longer removed.
```
export const PROPS = /** @&#8203;satisfies {Record<string, string>} */ ({
  prop: 0,
});
```
Contributed by @Conaclos

Linter

Promoted rules

New rules are incubated in the nursery group.
Once stable, we promote them to a stable group.

The following CSS rules are promoted:

The following JavaScript rules are promoted:

Deprecated rules

correctness/noInvalidNewBuiltin is deprecated. Use correctness/noInvalidBuiltinInstantiation instead.
style/useSingleCaseStatement is deprecated. Use correctness/noSwitchDeclarations instead.
suspicious/noConsoleLog is deprecated. Use suspicious/noConsole instead.

New features

Implement css suppression action. Contributed by @togami2864
Add support for GraphQL linting. Contributed by @ematipico
Add nursery/noCommonJs. Contributed by @minht11
Add nursery/noDuplicateCustomProperties. Contributed by @chansuke
Add nursery/noEnum. Contributed by @nickfla1
Add nursery/noDynamicNamespaceImportAccess. Contributed by @minht11
Add nursery/noIrregularWhitespace. Contributed by @michellocana
Add nursery/noRestrictedTypes. Contributed by @minht11
Add nursery/noSecrets. Contributed by @SaadBazaz
Add nursery/noUselessEscapeInRegex. Contributed by @Conaclos
Add nursery/noValueAtRule. Contributed by @rishabh3112
Add nursery/useAriaPropsSupportedByRole. Contributed by @ryo-ebata
Add nursery/useConsistentMemberAccessibility. Contributed by @seitarof
Add nursery/useStrictMode. Contributed by @ematipico
Add nursery/useTrimStartEnd. Contributed by @chansuke
Add nursery/noIrreguluarWhitespace. Contributed by @DerTimonius

Enhancements

Rename nursery/noUnknownSelectorPseudoElement to nursery/noUnknownPseudoElement. Contributed by @togami2864
The CSS linter is now enabled by default. Which means that you don't need to opt-in anymore using the configuration file biome.json:
```
{
-  "css": {
-    "linter": {
-      "enabled": true
-    }
-  }
}
```
Contributed by @ematipico
The JavaScript linter recognizes TypeScript 5.5 and 5.6 globals. Contributed by @Conaclos

noBlankTarget now supports an array of allowed domains.

The following configuration allows example.com and example.org as blank targets.

"linter": {
  "rules": {
    "a11y": {
      "noBlankTarget": {
      "level": "error",
        "options": {
           "allowDomains": ["example.com", "example.org"]
          }
        }
      }
    }
  }

Contributed by @Jayllyz

noConsole now accepts an option that specifies some allowed calls on console. Contributed by @Conaclos
Add an ignoreNull option for noDoubleEquals.

By default the rule allows loose comparisons against null.
The option ignoreNull can be set to false for reporting loose comparison against null.

Contributed by @peaBerberian.
noDuplicateObjectKeys now works for JSON and JSONC files. Contributed by @ematipico
noInvalidUseBeforeDeclaration now reports direct use of an enum member before its declaration.

In the following code, A is reported as use before its declaration.
```
enum E {
  B = A << 1,
  A = 1,
}
```
Contributed by @Conaclos
noNodejsModules now ignores imports of a package which has the same name as a Node.js module. Contributed by @Conaclos
noNodejsModules now ignores type-only imports (#1674).

The rule no longer reports type-only imports such as:
```
import type assert from "assert";
import type * as assert2 from "assert";
```
Contributed by @Conaclos
noRedundantUseStrict no longer reports "use strict" directives when the package.json marks explicitly the file as a script using the field "type": "commonjs". Contributed by @ematipico
noStaticOnlyClass no longer reports a class that extends another class (#3612). Contributed by @errmayank
noUndeclaredVariables no longer reports a direct reference to an enum member (#2974).

In the following code, the A reference is no longer reported as an undeclared variable.
```
enum E {
  A = 1,
  B = A << 1,
}
```
Contributed by @Conaclos
noUndeclaredVariables recognized Svelte 5 runes in Svelte components and svelte files.

Svelte 5 introduced runes.
The rule now recognizes Svelte 5 runes in files ending with the .svelte, .svelte.js or .svelte.ts extensions.

Contributed by @Conaclos
noUnusedVariables now checks TypeScript declaration files.

This allows to report a type that is unused because it isn't exported.
Global declarations files (declarations files without exports and imports) are still ignored.

Contributed by @Conaclos
useFilenamingConvention now supports unicase letters.

unicase letters have a single case: they are neither uppercase nor lowercase.
Biome now accepts filenames in unicase.
For example, the filename 안녕하세요 is now accepted.

We still reject a name that mixes unicase characters with lowercase or uppercase characters.
For example, the filename A안녕하세요 is rejected.

This change also fixes #3353.
Filenames consisting only of numbers are now accepted.

Contributed by @Conaclos
useFilenamingConvention now supports Next.js/Nuxt/Astro dynamic routes (#3465).

Next.js, SolidStart, Nuxt, and Astro support dynamic routes such as [...slug].js and [[...slug]].js.

Biome now recognizes this syntax. slug must contain only alphanumeric characters.

Contributed by @Conaclos
useExportType no longer reports empty export (#3535).

An empty export {} allows you to force TypeScript to consider a file with no imports and exports as an EcmaScript module.
While export type {} is valid, it is more common to use export {}.
Users may find it confusing that the linter asks them to convert it to export type {}.
Also, a bundler should be able to remove export {} as well as export type {}.
So it is not so useful to report export {}.

Contributed by @Conaclos

Bug fixes

noControlCharactersInRegex now corretcly handle \u escapes in unicode-aware regexes.

Previously, the rule didn't consider regex with the v flags as unicode-aware regexes.
Moreover, \uhhhh was not handled in unicode-aware regexes.

Contributed by @Conaclos
noControlCharactersInRegex now reports control characters and escape sequence of control characters in string regexes. Contributed by @Conaclos
noExcessiveNestedTestSuites: fix an edge case where the rule would alert on heavily nested zod schemas. Contributed by @dyc3
noExtraNonNullAssertion no longer reports a single non-null assertion enclosed in parentheses (#3352). Contributed by @Conaclos
noMultipleSpacesInRegularExpressionLiterals now correctly provides a code fix when Unicode characters are used. Contributed by @Conaclos
noRedeclare no longer report redeclartions for lexically scoped function declarations #3664.

In JavaScript strict mode, function declarations are lexically scoped:
they cannot be accessed outside the block where they are declared.

In non-strict mode, function declarations are hoisted to the top of the enclosing function or global scope.

Previously Biome always hoisted function declarations.
It now takes into account whether the code is in strict or non strict mode.

Contributed by @Conaclos
noUndeclaredDependencies now ignores self package imports.

Given teh following package.json:
```
{
  "name": "my-package",
  "main": "index.js"
}
```
The following import is no longer reported by the rule:
```
import * as mod from "my-package";
```
Contributed by @Conaclos
Fix [#3149] crashes that occurred when applying the noUselessFragments unsafe fixes in certain scenarios. Contributed by @unvalley
noRedeclare no longer reports a variable named as the function expression where it is declared. Contributed by @Conaclos
useAdjacentOverloadSignatures no longer reports a #private class member and a public class member that share the same name (#3309).

The following code is no longer reported:
```
class C {
  #f() {}
  g() {}
  f() {}
}
```
Contributed by @Conaclos
useAltText n olonger requests alt text for elements hidden from assistive technologies (#3316). Contributed by @robintown
useNamingConvention now accepts applying custom convention on abstract classes. Contributed by @Conaclos
useNamingConvention no longer suggests an empty fix when a name doesn't match strict Pascal case (#3561).

Previously the following code led useNamingConvention to suggest an empty fix.
The rule no longer provides a fix for this case.
```
type AAb = any
```
Contributed by @Conaclos
useNamingConvention no longer provides fixes for global TypeScript declaration files.

Global TypeScript declaration files have no epxorts and no imports.
All the declared types are available in all files of the project.
Thus, it is not safe to propose renaming only in the declaration file.

Contributed by @Conaclos
useSortedClasses lint error with Template literals (#3394). Contributed by @hangaoke1
useValidAriaValues now correctly check property types (3748).

Properties that expect a string now accept arbitrary text.
An identifiers can now be made up of any characters except ASCII whitespace.
An identifier list can now be separated by any ASCII whitespace.

Contributed by @Conaclos

Parser

Enhancements

The JSON parser now allows comments in turbo.json and jest.config.json. Contributed by @Netail and @Conaclos
The JSON parser now allows comments in files with the .json extension under the .vscode and .zed directories.

Biome recognizes are well known JSON files that allows comments and/or trailing commas.
Previously, Biome did not recognize JSON files under the .vscode and the .zed directories as JSON files that allow comments.
You had to configure Biome to recognize them:
```
{
  "overrides": [
    {
      "include": ["**/.vscode/*.json", "**/.zed/*.json"],
      "json": { "parser": { "allowComments": true } }
    }
  ]
}
```
This override is no longer needed!
Note that JSON files under the .vscode and the .zed directories don't accept trailing commas.

Contributed by @Conaclos

Bug fixes

The CSS parser now accepts emoji in identifiers (3627).

The following code is now correctly parsed:
```
p {
  --🥔-color: red;
  color: var(--🥔-color);
}
```
Contributed by @Conaclos
Fix #3287 nested selectors with pseudo-classes. Contributed by @denbezrukov
Fix #3349 allow CSS multiple ampersand support. Contributed by @denbezrukov
```
.class {
  && {
    color: red;
  }
}
```
Fix #3410 by correctly parsing break statements containing keywords.
```
out: while (true) {
  break out;
}
```
Contributed by @ah-yu
Fix #3464 by enabling JSX in .vue files that use the lang='jsx' or lang='tsx' attribute. Contributed by @ematipico

`v1.8.3`

Compare Source

CLI

Bug fixes

Fix #3104 by suppressing node warnings when using biome migrate. Contributed by @SuperchupuDev
Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @Sec-ant

Parser

Bug fixes

Implement CSS unicode range. Contributed by @denbezrukov

Formatter

Bug fixes

Fix #3184 CSS formatter converts custom identifiers to lowercase. Contributed by @denbezrukov
Fix #3256 constant crashes when editing css files #3256. Contributed by @denbezrukov

Linter

New features

Add nursery/useDeprecatedReason rule. Contributed by @vohoanglong0107.
Add nursery/noExportedImports. Contributed by @Conaclos

Bug fixes

useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @Conaclos
Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @ematipico
The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @Sec-ant

Enhancements

Enhance tailwind sorting lint rule #1274 with variant support.

Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order.
Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class.
Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight).
Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant.
Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last.
Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

Contributed by @lutaok

`v1.8.2`

Compare Source

CLI

Bug fixes

Fix #3201 by correctly injecting the source code of the file when printing the diagnostics. Contributed by @ematipico
Fix #3179 where comma separators are not correctly removed after running biome migrate and thus choke the parser. Contributed by @Sec-ant
Fix #3232 by correctly using the colors set by the user. Contributed by @ematipico

Enhancement

Reword the reporter message No fixes needed to No fixes applied.

The former message is misleading when there're still errors or warnings in the files that should be taken care of manually. For example:
```
Checked 2 files in <TIME>. No fixes needed.
Found 2 errors.
```
The new message suits better in these cases.

Contributed by @Sec-ant

Configuration

Bug fixes

Don't conceal previous overrides (#3176).

Previously, each override inherited the unset configuration of the base configuration.
This means that setting a configuration in an override can be concealed by a subsequent override that inherits of the value from the base configuration.

For example, in the next example, noDebugger was disabled for the index.js file.

{
  "linter": {
    "rules": {
      "suspicious": { "noDebugger": "off" }
    }
  },
  "overrides": [
    {
      "include": ["index.js"],
      "linter": {
        "rules": {
          "suspicious": { "noDebugger": "warn" }
        }
      }
    }, {
      "include": ["index.js"],
      "linter": {
        "rules": {
          "suspicious": { "noDoubleEquals": "off" }
        }
      }
    }
  ]
}

The rule is now correctly enabled for the index.js file.

Contributed by @Conaclos

Formatter

Bug fixes

Fix #3103 by correctly resolving CSS formatter options. Contributed by @ah-yu
Fix #3192 don't add an extra whitespace within :has. Contributed by @denbezrukov

JavaScript APIs

Bug fixes

Fix a regression introduced by the release of v1.8.0

Linter

New features

Add nursery/useValidAutocomplete. Contributed by @unvalley

Bug fixes

Add nursery/noShorthandPropertyOverrides. #2958 Contributed by @neokidev
Fix [#3084] false positive by correctly recognize parenthesized return statement. Contributed by @unvalley
useImportExtensions now suggests a correct fix for import '.' and import './.'. Contributed by @minht11
Fix useDateNow false positive when new Date object has arguments new Date(0).getTime(). Contributed by @minht11.
The noUnmatchableAnbSelector rule is now able to catch unmatchable an+b selectors like 0n+0 or -0n+0. Contributed by @Sec-ant.
The useHookAtTopLevel rule now recognizes properties named as hooks like foo.useFoo(). Contributed by @ksnyder9801
Fix #3092, prevent warning for Custom properties (--*). Contributed by @chansuke
Fix a false positive in the useLiteralKeys rule. (#3160)

This rule now ignores the following kind of computed member name:
```
const a = {
  [`line1
  line2`]: true,
};
```
Contributed by @Sec-ant
The noUnknownProperty rule now ignores the composes property often used in css modules. #3000 Contributed by @chansuke
Fix false positives of the useExhaustiveDependencies rule.

The component itself is considered stable when it is used recursively inside a hook closure defined inside of it:
```
import { useMemo } from "react";

function MyRecursiveComponent() {
  // MyRecursiveComponent is stable, we don't need to add it to the dependencies list.
  const children = useMemo(() => <MyRecursiveComponent />, []);
  return <div>{children}</div>;
}
```
Also, export default function and export default class are considered stable now because they can only appear at the top level of a module.

Contributed by @Sec-ant
Fix missing withDefaults macro in vue files for globals variables. Contributed by @Shyam-Chen

Parser

Bug fixes

Fix CSS modules settings mapping. Contributed by @denbezrukov

`v1.8.1`

Compare Source

Analyzer

CLI

Bug fixes

Fix #3069, prevent overwriting paths when using --staged or --changed options. Contributed by @unvalley
Fix a case where the file link inside a diagnostic wasn't correctly displayed inside a terminal run by VSCode. Contributed by @uncenter

Configuration

Bug fixes

Fix #3067, by assigning the correct default value to indentWidth. Contributed by @ematipico

Editors

Formatter

Bug fixes

Fix the bug where whitespace after the & character in CSS nesting was incorrectly trimmed, ensuring proper targeting of child classes #3061. Contributed by @denbezrukov
Fix #3068 where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by @denbezrukov
Fix the formatting of CSS grid layout properties. Contributed by @denbezrukov

JavaScript APIs

Linter

Bug fixes

The noEmptyBlock css lint rule now treats empty blocks containing comments as valid ones. Contributed by @Sec-ant
useLiteralKeys no longer reports quoted member names (#3085).

Previously useLiteralKeys reported quoted member names that can be unquoted.
For example, the rule suggested the following fix:
```
- const x = { "prop": 0 };
+ const x = { prop: 0 };
```
This conflicted with the option quoteProperties of our formatter.

The rule now ignores quoted member names.

Contributed by @Conaclos
noEmptyInterface now ignores empty interfaces in ambient modules (#3110). Contributed by @Conaclos
noUnusedVariables and noUnusedFunctionParameters no longer report the parameters of a constructor type (#3135).

Previously, arg was reported as unused in a constructor type like:
```
export type Classlike = new (arg: unknown) => string;
```
Contributed by @Conaclos
noStringCaseMismatch now ignores escape sequences (#3134).

The following code is no longer reported by the rule:
```
s.toUpperCase() === "\u001b";
```
Contributed by @Conaclos

Parser

New features

Implemented CSS Unknown At-Rule parsing, allowing the parser to gracefully handle unsupported or unrecognized CSS at-rules. Contributed by @denbezrukov

Bug fixes

Fix #3055 CSS: Layout using named grid lines is now correctly parsed. Contributed by @denbezrukov
Fix #3091. Allows the parser to handle nested style rules and at-rules properly, enhancing the parser's compatibility with the CSS Nesting Module. Contributed by @denbezrukov

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot requested a review from a team as a code owner June 10, 2024 13:53

renovate bot force-pushed the renovate/biomejs-biome-1.x branch from f25ca0a to f911f2e Compare June 20, 2024 12:55

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v1.8.1~~ chore(deps): update dependency @biomejs/biome to v1.8.2 Jun 20, 2024

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v1.8.2~~ chore(deps): update dependency @biomejs/biome to v1.8.3 Jun 27, 2024

renovate bot force-pushed the renovate/biomejs-biome-1.x branch from f911f2e to a327d90 Compare June 27, 2024 16:46

chore(deps): update dependency @biomejs/biome to v1.9.0

a16c0b9

renovate bot changed the title ~~chore(deps): update dependency @biomejs/biome to v1.8.3~~ chore(deps): update dependency @biomejs/biome to v1.9.0 Sep 12, 2024

renovate bot force-pushed the renovate/biomejs-biome-1.x branch from a327d90 to a16c0b9 Compare September 12, 2024 14:27

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency @biomejs/biome to v1.9.0 #418

chore(deps): update dependency @biomejs/biome to v1.9.0 #418

renovate bot commented Jun 10, 2024 •

edited

Loading

chore(deps): update dependency @biomejs/biome to v1.9.0 #418

Are you sure you want to change the base?

chore(deps): update dependency @biomejs/biome to v1.9.0 #418

Conversation

renovate bot commented Jun 10, 2024 • edited Loading

Release Notes

v1.9.0

Analyzer

CLI

New features

Enhancements

Bug fixes

Configuration

Editors

Formatter

Linter

Promoted rules

Deprecated rules

New features

Enhancements

Bug fixes

Parser

Enhancements

Bug fixes

v1.8.3

CLI

Bug fixes

Parser

Bug fixes

Formatter

Bug fixes

Linter

New features

Bug fixes

Enhancements

v1.8.2

CLI

Bug fixes

Enhancement

Configuration

Bug fixes

Formatter

Bug fixes

JavaScript APIs

Bug fixes

Linter

New features

Bug fixes

Parser

Bug fixes

v1.8.1

Analyzer

CLI

Bug fixes

Configuration

Bug fixes

Editors

Formatter

Bug fixes

JavaScript APIs

Linter

Bug fixes

Parser

New features

Bug fixes

Configuration

renovate bot commented Jun 10, 2024 •

edited

Loading

`v1.9.0`

`v1.8.3`

`v1.8.2`

`v1.8.1`